home *** CD-ROM | disk | FTP | other *** search
- Date: Tue, 31 May 1994 14:05:10 -0400 (EDT)
- From: Timothy Miller <millert@undergrad.csee.usf.edu>
- Subject: Re: MAUS
- To: gem-list@world.std.com
- In-Reply-To: <memo.248351@cix.compulink.co.uk>
- Message-Id: <Pine.3.87.9405311410.C24733-0100000@undergrad>
- Mime-Version: 1.0
- Precedence: bulk
-
-
-
- On Tue, 31 May 1994, Andre Willey wrote:
-
- >
- > In-Reply-To: <Pine.3.87.9405302346.A19277-0100000@undergrad>
- >
- > In <Pine.3.87.9405302346.A19277-0100000@undergrad>,
- > millert@undergrad.csee.usf.edu wrote:
- >
- > > On a further note, shift-backspace and shift-delete should each delete
- > > a SINGLE character.
- >
- > No, I like Control and Shift delete for delete line (prehaps from cursor?)
- > and delete word. As long as they can be undone, there isn't really a
- > problem.
- >
- > Andre
- >
-
- Imageine typing this:
-
- ... should each delete a SINHL...
-
- you're holding down shift with your little finger and at the moment you
- hit L, you realize that the H should have been a G, so you instinctively
- hit backspace and then finish with the rest of 'GLE.....'. When you look
- back, you realize suddenly that you're line STARTS with 'GLE' and all the
- stuff before that has been wiped. And then you realize that UNDO doesn't
- recover the line either because of all the stuff you typed after you
- erased the line. The user shouldn't have to put up with this because the
- userinterface designer should be aware of dangerous keycombinations.
-
- Using ctrl to modify backspace and delete is fine, but not shift.
-
- Listen, folks, we have to be nitpickingly careful about this stuff, or
- we're going to end up with crap. If we have things in this standard that
- are COUNTERPRODUCTIVE, then we defeat the purpose of HAVING the standard.
-
-